Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 01843467bf5aaed4a2c2990a03ea9e2432f038469be8c02bf69d881dcc7042ec

Tx prefix hash: 81ef65578b2fd2727626796adf9b293db1d99a97aaa062a7a15a7948c23239b0
Tx public key: 8b2f77456b2287c8685d1a52f9e4da1ee4ab32119129dd0e5d47b3184dbf0015
Timestamp: 1745935263 Timestamp [UCT]: 2025-04-29 14:01:03 Age [y:d:h:m:s]: 00:254:03:44:12
Block: 1272069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179420 RingCT/type: yes/0
Extra: 018b2f77456b2287c8685d1a52f9e4da1ee4ab32119129dd0e5d47b3184dbf001502110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26de0807b042f76f736e40021816f5ae8d49a8bbafa2fbc57355e7e9f1265159 0.600000000000 1759342 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1272079, "vin": [ { "gen": { "height": 1272069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26de0807b042f76f736e40021816f5ae8d49a8bbafa2fbc57355e7e9f1265159" } } ], "extra": [ 1, 139, 47, 119, 69, 107, 34, 135, 200, 104, 93, 26, 82, 249, 228, 218, 30, 228, 171, 50, 17, 145, 41, 221, 14, 93, 71, 179, 24, 77, 191, 0, 21, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8