Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4412862b6e22e2f05cf7193c1c7e5901acdf4e99eeb3c200b198c8c88790a744

Tx prefix hash: 8721af688152631f513f6eb6c829f33ad1578a5f34c6faea4f936dcbcb53a595
Tx public key: 32456b709c336632707d5dc239810ed4cd233465ec5800bedc42021c4fdf4ce7
Timestamp: 1694238802 Timestamp [UCT]: 2023-09-09 05:53:22 Age [y:d:h:m:s]: 01:206:21:40:09
Block: 844162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408968 RingCT/type: yes/0
Extra: 0132456b709c336632707d5dc239810ed4cd233465ec5800bedc42021c4fdf4ce702110000000275e3f0e9000000000000000000

1 output(s) for total of 0.979356772000 dcy

stealth address amount amount idx
00: fee2a9c1bbf2f003e4de0ab964b988f1cef86d46035bd548df1516cc876e251e 0.979356772000 1297454 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": 844172, "vin": [ { "gen": { "height": 844162 } } ], "vout": [ { "amount": 979356772, "target": { "key": "fee2a9c1bbf2f003e4de0ab964b988f1cef86d46035bd548df1516cc876e251e" } } ], "extra": [ 1, 50, 69, 107, 112, 156, 51, 102, 50, 112, 125, 93, 194, 57, 129, 14, 212, 205, 35, 52, 101, 236, 88, 0, 190, 220, 66, 2, 28, 79, 223, 76, 231, 2, 17, 0, 0, 0, 2, 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