Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f44fad2c67d13a4d15d9345f919b600c78d225d6af6b596bb5dcc4728174a26d

Tx prefix hash: 514f07e0f41c817d2d089584df2ede2dada87fbffdc0843fdaae72b9a109d9fc
Tx public key: f2e6267f2921072b9e561c0173a032cac48d9978e4acdc3e1ca1f22787c9719e
Timestamp: 1703841912 Timestamp [UCT]: 2023-12-29 09:25:12 Age [y:d:h:m:s]: 01:313:03:22:15
Block: 923595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482612 RingCT/type: yes/0
Extra: 01f2e6267f2921072b9e561c0173a032cac48d9978e4acdc3e1ca1f22787c9719e0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 637bbd0e28d739aea54d97eae6ebe3f981114453541974599897014aa15d7270 0.600000000000 1381327 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": 923605, "vin": [ { "gen": { "height": 923595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "637bbd0e28d739aea54d97eae6ebe3f981114453541974599897014aa15d7270" } } ], "extra": [ 1, 242, 230, 38, 127, 41, 33, 7, 43, 158, 86, 28, 1, 115, 160, 50, 202, 196, 141, 153, 120, 228, 172, 220, 62, 28, 161, 242, 39, 135, 201, 113, 158, 2, 17, 0, 0, 0, 2, 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