Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c731c133dcc1519c3f640c5550a47e9d01b54b51f36e36fa17a22f390ae3a8a5

Tx prefix hash: 6999c15b5d0cc6276bcd218a50be479ee0eea5c8d80fa2713e48b87d1e8dcba6
Tx public key: 5228e938087c2e4bbbff40207d7fdc9dc513120177a7488133d1dcb14ad4a01f
Timestamp: 1725469392 Timestamp [UCT]: 2024-09-04 17:03:12 Age [y:d:h:m:s]: 00:171:18:22:24
Block: 1102903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122562 RingCT/type: yes/0
Extra: 015228e938087c2e4bbbff40207d7fdc9dc513120177a7488133d1dcb14ad4a01f02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d39a1594a30458fd117f2bf54a154fb3294dfb89066ebc5f9c3c3e101e4239f0 0.600000000000 1579520 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": 1102913, "vin": [ { "gen": { "height": 1102903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d39a1594a30458fd117f2bf54a154fb3294dfb89066ebc5f9c3c3e101e4239f0" } } ], "extra": [ 1, 82, 40, 233, 56, 8, 124, 46, 75, 187, 255, 64, 32, 125, 127, 220, 157, 197, 19, 18, 1, 119, 167, 72, 129, 51, 209, 220, 177, 74, 212, 160, 31, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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