Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf00a1a7635fc5227730b2e3155507b8c4a68f547d3473cfd1e3b703cadbc970

Tx prefix hash: 32b7cf72a87c9027818e28681d90193eb2b252fd645f70f368a31330e10b552b
Tx public key: 613b1f130d906b8f84e4b23eb0bb892c910f9c34e252b21834015a1a3fa0c2c4
Timestamp: 1708584486 Timestamp [UCT]: 2024-02-22 06:48:06 Age [y:d:h:m:s]: 01:038:04:59:53
Block: 962920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288324 RingCT/type: yes/0
Extra: 01613b1f130d906b8f84e4b23eb0bb892c910f9c34e252b21834015a1a3fa0c2c402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe45beb647d1c2e5a4e3971cb957403b1a408914b4cb611bfecb1439a689722b 0.600000000000 1422609 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": 962930, "vin": [ { "gen": { "height": 962920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe45beb647d1c2e5a4e3971cb957403b1a408914b4cb611bfecb1439a689722b" } } ], "extra": [ 1, 97, 59, 31, 19, 13, 144, 107, 143, 132, 228, 178, 62, 176, 187, 137, 44, 145, 15, 156, 52, 226, 82, 178, 24, 52, 1, 90, 26, 63, 160, 194, 196, 2, 17, 0, 0, 0, 1, 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