Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e10886c5e2b3d0d4ed4412943067c81773f6a37d879a3e3f6a2370e4182d0be

Tx prefix hash: 8231dea1135d42b010c247276bf99bf03045f5a74e33266121fb0c59c645e6be
Tx public key: 10b938854747b9835cca742f7de74c30b119abfcc0a04fba04ceee58b1d26826
Timestamp: 1705589344 Timestamp [UCT]: 2024-01-18 14:49:04 Age [y:d:h:m:s]: 01:003:23:06:39
Block: 938063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264111 RingCT/type: yes/0
Extra: 0110b938854747b9835cca742f7de74c30b119abfcc0a04fba04ceee58b1d2682602110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 827bb4c780a46058e8e76d8ea0b0de5b59b7833134d2aeed9d6afd6dc41d9aea 0.600000000000 1396127 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": 938073, "vin": [ { "gen": { "height": 938063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "827bb4c780a46058e8e76d8ea0b0de5b59b7833134d2aeed9d6afd6dc41d9aea" } } ], "extra": [ 1, 16, 185, 56, 133, 71, 71, 185, 131, 92, 202, 116, 47, 125, 231, 76, 48, 177, 25, 171, 252, 192, 160, 79, 186, 4, 206, 238, 88, 177, 210, 104, 38, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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