Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67c70ac8e88c1a75c795767f8155992dd4618fca830a384b64a099c6c952f145

Tx prefix hash: 3e755a11cf3bf59d0b8ea56e7152455416fb2e90336a20aa9ca413b34f02beb9
Tx public key: 67939cec6fa12516fd785e8df0116253a085a7b25746fe7e91de8dac8490f3d4
Timestamp: 1725190765 Timestamp [UCT]: 2024-09-01 11:39:25 Age [y:d:h:m:s]: 00:219:15:02:07
Block: 1100590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156813 RingCT/type: yes/0
Extra: 0167939cec6fa12516fd785e8df0116253a085a7b25746fe7e91de8dac8490f3d4021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e285d92b1e843137a4915792f87c81b8a2970b83793b190e09c784d1b3cf2c33 0.600000000000 1576569 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": 1100600, "vin": [ { "gen": { "height": 1100590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e285d92b1e843137a4915792f87c81b8a2970b83793b190e09c784d1b3cf2c33" } } ], "extra": [ 1, 103, 147, 156, 236, 111, 161, 37, 22, 253, 120, 94, 141, 240, 17, 98, 83, 160, 133, 167, 178, 87, 70, 254, 126, 145, 222, 141, 172, 132, 144, 243, 212, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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