Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 504a0207d6b52289dd85215f9edb9f1f468aaf7d0bb5b1d2a203ce96c04dcedb

Tx prefix hash: 902206231d7dccfbbb78c8a5a11b63f61e06e947a704b9ee36b9a09ca43624ff
Tx public key: 893d4a7d7c6278122b28f9fc3eee6e14970c7763b68035d1958b1b72bb3dcc81
Timestamp: 1736783233 Timestamp [UCT]: 2025-01-13 15:47:13 Age [y:d:h:m:s]: 00:157:19:22:04
Block: 1196553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112454 RingCT/type: yes/0
Extra: 01893d4a7d7c6278122b28f9fc3eee6e14970c7763b68035d1958b1b72bb3dcc8102110000000e1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bad3937de5ba31cf61c6534615f4e1051f89f7983a37d638fd638ae6938757c3 0.600000000000 1683152 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": 1196563, "vin": [ { "gen": { "height": 1196553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bad3937de5ba31cf61c6534615f4e1051f89f7983a37d638fd638ae6938757c3" } } ], "extra": [ 1, 137, 61, 74, 125, 124, 98, 120, 18, 43, 40, 249, 252, 62, 238, 110, 20, 151, 12, 119, 99, 182, 128, 53, 209, 149, 139, 27, 114, 187, 61, 204, 129, 2, 17, 0, 0, 0, 14, 31, 10, 83, 235, 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