Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0b1df76809a233304706e1822d76b1cdbedf3c5741f4da17be39f1330962cad

Tx prefix hash: daf4d0f83730e6f09a64aee2ff6dcf9c3d4a3430d80236caa6a3a48e4042fa2d
Tx public key: 4831f217f3a6d9c24310f55aeaf012e86480888449cb0cdf97e37de92ead27c5
Timestamp: 1713782258 Timestamp [UCT]: 2024-04-22 10:37:38 Age [y:d:h:m:s]: 01:045:15:34:39
Block: 1006013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293584 RingCT/type: yes/0
Extra: 014831f217f3a6d9c24310f55aeaf012e86480888449cb0cdf97e37de92ead27c502110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a69dc666c9c10ffac635e2dfb214633fd9617b568161eaadbf128d42fcdcfc97 0.600000000000 1466897 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": 1006023, "vin": [ { "gen": { "height": 1006013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a69dc666c9c10ffac635e2dfb214633fd9617b568161eaadbf128d42fcdcfc97" } } ], "extra": [ 1, 72, 49, 242, 23, 243, 166, 217, 194, 67, 16, 245, 90, 234, 240, 18, 232, 100, 128, 136, 132, 73, 203, 12, 223, 151, 227, 125, 233, 46, 173, 39, 197, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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