Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab231a1c8bf1b49ffed957cd1599cf46714daa810027447802f64e65f0440d44

Tx prefix hash: 035bd9668d611cc09d4d9c5ea45ba30e23ec10dbd370d30769afa88f001572ab
Tx public key: cf2fcc4cff1710c3474454d78589b9b8c647e292456c87a63dc4e82a511e145d
Timestamp: 1698220152 Timestamp [UCT]: 2023-10-25 07:49:12 Age [y:d:h:m:s]: 01:219:05:23:26
Block: 877206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417736 RingCT/type: yes/0
Extra: 01cf2fcc4cff1710c3474454d78589b9b8c647e292456c87a63dc4e82a511e145d02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.761118702000 dcy

stealth address amount amount idx
00: 83b644fbb2a8cf01d4a9ffae11d4fcf91f7478950fe9080f974e2b103be72bc4 0.761118702000 1332572 of 0

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": 877216, "vin": [ { "gen": { "height": 877206 } } ], "vout": [ { "amount": 761118702, "target": { "key": "83b644fbb2a8cf01d4a9ffae11d4fcf91f7478950fe9080f974e2b103be72bc4" } } ], "extra": [ 1, 207, 47, 204, 76, 255, 23, 16, 195, 71, 68, 84, 215, 133, 137, 185, 184, 198, 71, 226, 146, 69, 108, 135, 166, 61, 196, 232, 42, 81, 30, 20, 93, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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