Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8c1894e44242e92e4bcf23a834c0d1cf2d7f5a40cdf642ffac73a77464dcff4

Tx prefix hash: 764f601d6ea62b279754699a8f689ed52bef9480d5810367d0c0123382864a15
Tx public key: cb42fc8310a0b2442df3b65c71762fe73a1672ad9e82943e82c88be3620ceb02
Timestamp: 1734648899 Timestamp [UCT]: 2024-12-19 22:54:59 Age [y:d:h:m:s]: 00:098:23:23:42
Block: 1178910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70498 RingCT/type: yes/0
Extra: 01cb42fc8310a0b2442df3b65c71762fe73a1672ad9e82943e82c88be3620ceb020211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e36db0d001e39b89d39da66d218bd576b5c39a0229b70c9c8a95cf4c82b8d458 0.600000000000 1665301 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": 1178920, "vin": [ { "gen": { "height": 1178910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e36db0d001e39b89d39da66d218bd576b5c39a0229b70c9c8a95cf4c82b8d458" } } ], "extra": [ 1, 203, 66, 252, 131, 16, 160, 178, 68, 45, 243, 182, 92, 113, 118, 47, 231, 58, 22, 114, 173, 158, 130, 148, 62, 130, 200, 139, 227, 98, 12, 235, 2, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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