Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64438e260c6d3574a6f0cf7297d1f851ee3562fdec38644521a34d9605ab5624

Tx prefix hash: b395ac46d34b2e81ae061f7d8291397615d1fc252ab39b4332afbec4455aa206
Tx public key: 1f634cdf1fae02e4dc59c7e2fc971795268a9c6bc691aea17516dae8c9311467
Timestamp: 1705024010 Timestamp [UCT]: 2024-01-12 01:46:50 Age [y:d:h:m:s]: 01:067:09:53:01
Block: 933376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309300 RingCT/type: yes/0
Extra: 011f634cdf1fae02e4dc59c7e2fc971795268a9c6bc691aea17516dae8c931146702110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d345a88de08ffe3d4b07a6c58a29bedc3e31d586d0ac4f9e69f52475d2e7e6cb 0.600000000000 1391338 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": 933386, "vin": [ { "gen": { "height": 933376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d345a88de08ffe3d4b07a6c58a29bedc3e31d586d0ac4f9e69f52475d2e7e6cb" } } ], "extra": [ 1, 31, 99, 76, 223, 31, 174, 2, 228, 220, 89, 199, 226, 252, 151, 23, 149, 38, 138, 156, 107, 198, 145, 174, 161, 117, 22, 218, 232, 201, 49, 20, 103, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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