Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25afd8dc81ee939a126d08dbb5efdc4c3ec4cbd0b6672d70c8cc18564babfd0c

Tx prefix hash: 95afbe7ba6e9d4c89c34945dcbd7d0fd22d97e5f0a27eb2d4120345dde7f9535
Tx public key: 6c855ae36440bf5d2f163efb849179d85b6c8587d64cdd42483eed722ae39e34
Timestamp: 1671840357 Timestamp [UCT]: 2022-12-24 00:05:57 Age [y:d:h:m:s]: 02:105:17:06:38
Block: 659166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 597230 RingCT/type: yes/0
Extra: 016c855ae36440bf5d2f163efb849179d85b6c8587d64cdd42483eed722ae39e3402110000000283600029000000000000000000

1 output(s) for total of 4.017069839000 dcy

stealth address amount amount idx
00: ef0d2206fc1f5cd85cd05d1f1ce44caea58f3e6792d0b3de9f8732141f4ff9a3 4.017069839000 1099861 of 0

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": 659176, "vin": [ { "gen": { "height": 659166 } } ], "vout": [ { "amount": 4017069839, "target": { "key": "ef0d2206fc1f5cd85cd05d1f1ce44caea58f3e6792d0b3de9f8732141f4ff9a3" } } ], "extra": [ 1, 108, 133, 90, 227, 100, 64, 191, 93, 47, 22, 62, 251, 132, 145, 121, 216, 91, 108, 133, 135, 214, 76, 221, 66, 72, 62, 237, 114, 42, 227, 158, 52, 2, 17, 0, 0, 0, 2, 131, 96, 0, 41, 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