Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce3cda73b8a745e0f24180a18966b90a7b733efdafcb087b59888d05fb6214ef

Tx prefix hash: 09f5bc4b3a7c9aca7634bfd154877e86d960e598b3537593a7f8b394ea26780a
Tx public key: e9729a8791c8e43274fef138ba36e87f87a246a90df94073b3da423ae5ac5fc3
Timestamp: 1727575708 Timestamp [UCT]: 2024-09-29 02:08:28 Age [y:d:h:m:s]: 00:060:12:57:52
Block: 1120365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43271 RingCT/type: yes/0
Extra: 01e9729a8791c8e43274fef138ba36e87f87a246a90df94073b3da423ae5ac5fc302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee4b6eec330aa2f07f125a25c4a7929ba878a2c071138bcf1c957437b7094702 0.600000000000 1602254 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": 1120375, "vin": [ { "gen": { "height": 1120365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee4b6eec330aa2f07f125a25c4a7929ba878a2c071138bcf1c957437b7094702" } } ], "extra": [ 1, 233, 114, 154, 135, 145, 200, 228, 50, 116, 254, 241, 56, 186, 54, 232, 127, 135, 162, 70, 169, 13, 249, 64, 115, 179, 218, 66, 58, 229, 172, 95, 195, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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