Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d301cc6a31ef881d88d93ceef74ecd4a6a53e3e25e9bdd5b31c381129af3638

Tx prefix hash: 623ed36b52d1daaaedddb7e1b804b164481b73853a31b12f14175052da540160
Tx public key: 753aa6ee5f393af3f3d0f9761f5e76e3298e2ce2d4cc10b3c35c659d29b639ab
Timestamp: 1717775600 Timestamp [UCT]: 2024-06-07 15:53:20 Age [y:d:h:m:s]: 01:155:03:46:00
Block: 1039123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369460 RingCT/type: yes/0
Extra: 01753aa6ee5f393af3f3d0f9761f5e76e3298e2ce2d4cc10b3c35c659d29b639ab02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cc04bdc3d8cc31ab050542ca2d73622182dd7617e7933f058a8229986083fa6 0.600000000000 1507726 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": 1039133, "vin": [ { "gen": { "height": 1039123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cc04bdc3d8cc31ab050542ca2d73622182dd7617e7933f058a8229986083fa6" } } ], "extra": [ 1, 117, 58, 166, 238, 95, 57, 58, 243, 243, 208, 249, 118, 31, 94, 118, 227, 41, 142, 44, 226, 212, 204, 16, 179, 195, 92, 101, 157, 41, 182, 57, 171, 2, 17, 0, 0, 0, 5, 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