Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79733a6f2fa5d86448fc5e0fd9436ee0e1c67a226501eab893e009ead9c7549a

Tx prefix hash: 8e9a802028918a464459bb1c6cbba87d8d2d3b8a647f74cef64d5e6495c67cdb
Tx public key: 6de948136eedcb23e8a504f729381a1fa61c53b9cbf5cae19691e9221940ff91
Timestamp: 1712766700 Timestamp [UCT]: 2024-04-10 16:31:40 Age [y:d:h:m:s]: 01:237:12:12:11
Block: 997561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428475 RingCT/type: yes/0
Extra: 016de948136eedcb23e8a504f729381a1fa61c53b9cbf5cae19691e9221940ff910211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 552ca06395c8fd0ee2d06c23600ca9018e3b0161b1f7c1e2b09e8289f530181d 0.600000000000 1457993 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": 997571, "vin": [ { "gen": { "height": 997561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "552ca06395c8fd0ee2d06c23600ca9018e3b0161b1f7c1e2b09e8289f530181d" } } ], "extra": [ 1, 109, 233, 72, 19, 110, 237, 203, 35, 232, 165, 4, 247, 41, 56, 26, 31, 166, 28, 83, 185, 203, 245, 202, 225, 150, 145, 233, 34, 25, 64, 255, 145, 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