Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbe4ef63a131429036fc90e5014d2686c2e61a52396cc99399b199aa9bf27200

Tx prefix hash: c57339dd776608a3b257cead95e44428911f5dc8f675913a7083b2661e205f74
Tx public key: 1b81dfd4c10fbf2a2cc8bf6cbcfde2fc34ef17b28e4172689e1c9ebc40dab625
Timestamp: 1702967782 Timestamp [UCT]: 2023-12-19 06:36:22 Age [y:d:h:m:s]: 01:121:12:25:10
Block: 916363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347974 RingCT/type: yes/0
Extra: 011b81dfd4c10fbf2a2cc8bf6cbcfde2fc34ef17b28e4172689e1c9ebc40dab625021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c7e9e06a2e819ffea4be5ccfe123a0912358cc9a4e327293b91c9059aea180f 0.600000000000 1373863 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": 916373, "vin": [ { "gen": { "height": 916363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c7e9e06a2e819ffea4be5ccfe123a0912358cc9a4e327293b91c9059aea180f" } } ], "extra": [ 1, 27, 129, 223, 212, 193, 15, 191, 42, 44, 200, 191, 108, 188, 253, 226, 252, 52, 239, 23, 178, 142, 65, 114, 104, 158, 28, 158, 188, 64, 218, 182, 37, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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