Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36411361c54cfecda86b9ccd6a1e6b479d9f942d51e4eb9e4366b308ef7f0031

Tx prefix hash: 354d2e44feffc57cb17bec348a060e39f974c0f94de77e4737376c993519e3eb
Tx public key: 7298285a497b0b87ea24775948ff35fb309f1b4122ce0b23e5b4ced86d8ddb00
Timestamp: 1704111177 Timestamp [UCT]: 2024-01-01 12:12:57 Age [y:d:h:m:s]: 01:058:17:53:17
Block: 925820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303074 RingCT/type: yes/0
Extra: 017298285a497b0b87ea24775948ff35fb309f1b4122ce0b23e5b4ced86d8ddb000211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb9d38e906bb9a4d515bb739319f1423b1840f932699ba250c53883a5c063334 0.600000000000 1383590 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": 925830, "vin": [ { "gen": { "height": 925820 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb9d38e906bb9a4d515bb739319f1423b1840f932699ba250c53883a5c063334" } } ], "extra": [ 1, 114, 152, 40, 90, 73, 123, 11, 135, 234, 36, 119, 89, 72, 255, 53, 251, 48, 159, 27, 65, 34, 206, 11, 35, 229, 180, 206, 216, 109, 141, 219, 0, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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