Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c36b464c6ae86ce40a6ac71bc137c1d7019c2d48f6c7826be22ca32d0b12cb3b

Tx prefix hash: ef2200a7db791c8872af6598ebcfab9696be7a4ed7b52532bce765dd25260a38
Tx public key: 678216539c8c40c17fd7f3265ff1b35049e8f986937e9638e8a4705ecc5df2af
Timestamp: 1712149850 Timestamp [UCT]: 2024-04-03 13:10:50 Age [y:d:h:m:s]: 00:218:00:04:08
Block: 992446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156102 RingCT/type: yes/0
Extra: 01678216539c8c40c17fd7f3265ff1b35049e8f986937e9638e8a4705ecc5df2af02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9af61dc30332f306e4a8a3399484b503be8dae75d87d4a140a1860985eeb1cbe 0.600000000000 1452788 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": 992456, "vin": [ { "gen": { "height": 992446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9af61dc30332f306e4a8a3399484b503be8dae75d87d4a140a1860985eeb1cbe" } } ], "extra": [ 1, 103, 130, 22, 83, 156, 140, 64, 193, 127, 215, 243, 38, 95, 241, 179, 80, 73, 232, 249, 134, 147, 126, 150, 56, 232, 164, 112, 94, 204, 93, 242, 175, 2, 17, 0, 0, 0, 3, 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