Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33dd1cedf5167b4aecb18ac044e11b6ee3429835bac7747e3b14d04e7a1fcadb

Tx prefix hash: f846c0a86860c0bb15e3d6570309f712e1f4f185999841752ac2537d3dc317d6
Tx public key: 6d24085e0db8963457dee4c52508fb5546835a6563d89e53307526a3f6f05bee
Timestamp: 1712733183 Timestamp [UCT]: 2024-04-10 07:13:03 Age [y:d:h:m:s]: 01:270:14:56:02
Block: 997290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452192 RingCT/type: yes/0
Extra: 016d24085e0db8963457dee4c52508fb5546835a6563d89e53307526a3f6f05bee021100000004e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4e40689cf4289f5b34f9f555d6709ba920be3298c9795b9e2f2bdcc73e42a19 0.600000000000 1457720 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": 997300, "vin": [ { "gen": { "height": 997290 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4e40689cf4289f5b34f9f555d6709ba920be3298c9795b9e2f2bdcc73e42a19" } } ], "extra": [ 1, 109, 36, 8, 94, 13, 184, 150, 52, 87, 222, 228, 197, 37, 8, 251, 85, 70, 131, 90, 101, 99, 216, 158, 83, 48, 117, 38, 163, 246, 240, 91, 238, 2, 17, 0, 0, 0, 4, 224, 133, 50, 182, 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