Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b24bb26c3aada7e767fefdbccef7e22e23f99ccbe9dc128b41aee86b46f52b1e

Tx prefix hash: 52248b2b41668ca373a19fd4c62e059426cc1466f2346f1c719df285ae08a360
Tx public key: 3f5ef1a83197a65c91f2f777fa3dc63aed9f5ae32d330f36f75da0196934fda1
Timestamp: 1709496138 Timestamp [UCT]: 2024-03-03 20:02:18 Age [y:d:h:m:s]: 01:249:08:40:14
Block: 970478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436940 RingCT/type: yes/0
Extra: 013f5ef1a83197a65c91f2f777fa3dc63aed9f5ae32d330f36f75da0196934fda102110000000149a185bb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b281f433c789faf2717e350d076197e5b241b2aaf53760384e234ed00b4ca4e 0.600000000000 1430333 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": 970488, "vin": [ { "gen": { "height": 970478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b281f433c789faf2717e350d076197e5b241b2aaf53760384e234ed00b4ca4e" } } ], "extra": [ 1, 63, 94, 241, 168, 49, 151, 166, 92, 145, 242, 247, 119, 250, 61, 198, 58, 237, 159, 90, 227, 45, 51, 15, 54, 247, 93, 160, 25, 105, 52, 253, 161, 2, 17, 0, 0, 0, 1, 73, 161, 133, 187, 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