Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 998b2b0257d8aa704ccf7d47cf4e2131ca9f8969526651629b2b77378ec9b77b

Tx prefix hash: 0ad7139a811cae03e6f6825306ddd8b033431edc319c68f4734715fbc95f4ad9
Tx public key: 598cafb5c90bdbdd627754b4a422b8414270472935bc4099bb20924d425d0c66
Timestamp: 1660428609 Timestamp [UCT]: 2022-08-13 22:10:09 Age [y:d:h:m:s]: 02:245:10:34:13
Block: 565236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 696644 RingCT/type: yes/0
Extra: 01598cafb5c90bdbdd627754b4a422b8414270472935bc4099bb20924d425d0c66021100000001faf35c9c000000000000000000

1 output(s) for total of 8.225051034000 dcy

stealth address amount amount idx
00: baf0323a3f9521ef19ecad9b5570a7e09c9312a6cc9a3d078f78594149ea8bc1 8.225051034000 998112 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": 565246, "vin": [ { "gen": { "height": 565236 } } ], "vout": [ { "amount": 8225051034, "target": { "key": "baf0323a3f9521ef19ecad9b5570a7e09c9312a6cc9a3d078f78594149ea8bc1" } } ], "extra": [ 1, 89, 140, 175, 181, 201, 11, 219, 221, 98, 119, 84, 180, 164, 34, 184, 65, 66, 112, 71, 41, 53, 188, 64, 153, 187, 32, 146, 77, 66, 93, 12, 102, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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