Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d53d81b2159a24d8c6bc5ab3b4791a7d212bc78c679f307bf5d631350f6721ca

Tx prefix hash: dd5f11ca38e05bc0064b3d53e3c9620b144966a6fe31a4ccf038b16f0642e44d
Tx public key: 7e1e6ee36fe959d7495d17373ba0e2a3657338d077488363358fcb7f88b49b49
Timestamp: 1731810348 Timestamp [UCT]: 2024-11-17 02:25:48 Age [y:d:h:m:s]: 00:214:14:55:41
Block: 1155364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153140 RingCT/type: yes/0
Extra: 017e1e6ee36fe959d7495d17373ba0e2a3657338d077488363358fcb7f88b49b49021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f64cf5934a331927c6707f526e60f2d40f0136136b90f716de47f9c40b925e25 0.600000000000 1640979 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": 1155374, "vin": [ { "gen": { "height": 1155364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f64cf5934a331927c6707f526e60f2d40f0136136b90f716de47f9c40b925e25" } } ], "extra": [ 1, 126, 30, 110, 227, 111, 233, 89, 215, 73, 93, 23, 55, 59, 160, 226, 163, 101, 115, 56, 208, 119, 72, 131, 99, 53, 143, 203, 127, 136, 180, 155, 73, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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