Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a315be81d61a812349f6e504e60bc15295da73fdf91f95f49a4f0c159d15a6c6

Tx prefix hash: 4aa2fb59b8308a578bf1517417575708e31baafbe8cfb3c5e5065cbf51a42c6e
Tx public key: 0c2f93c855298720ba1e5e650db655dcab255d1e858bbbfccbcb2e9f7d0a9d47
Timestamp: 1741258657 Timestamp [UCT]: 2025-03-06 10:57:37 Age [y:d:h:m:s]: 00:006:07:04:58
Block: 1233346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4508 RingCT/type: yes/0
Extra: 010c2f93c855298720ba1e5e650db655dcab255d1e858bbbfccbcb2e9f7d0a9d47021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd8a424cebbbdadcb5fbf399540bd3cd274ebf698b1a4d01f12f5cbb67064b73 0.600000000000 1720265 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": 1233356, "vin": [ { "gen": { "height": 1233346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd8a424cebbbdadcb5fbf399540bd3cd274ebf698b1a4d01f12f5cbb67064b73" } } ], "extra": [ 1, 12, 47, 147, 200, 85, 41, 135, 32, 186, 30, 94, 101, 13, 182, 85, 220, 171, 37, 93, 30, 133, 139, 187, 252, 203, 203, 46, 159, 125, 10, 157, 71, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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