Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e66f9ac7329c4ccc9fa56a0f801b0ce93533aff8ee7758ab043c21d8431bb979

Tx prefix hash: 2cb89462d28f9eb982aeda0b1e3e71b7e86bdf3f79a94a58231388fa7df83e27
Tx public key: ad03ea4a77d7e501cdc903dae7e9fb49296f0a5f324c8e67f4f06364b171ea60
Timestamp: 1734269350 Timestamp [UCT]: 2024-12-15 13:29:10 Age [y:d:h:m:s]: 00:108:04:37:22
Block: 1175768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77092 RingCT/type: yes/0
Extra: 01ad03ea4a77d7e501cdc903dae7e9fb49296f0a5f324c8e67f4f06364b171ea600211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 131fa005feb8cd888c5f7a178ee4564a6344373d70b9fbd89a4638f2089738c3 0.600000000000 1662091 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": 1175778, "vin": [ { "gen": { "height": 1175768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "131fa005feb8cd888c5f7a178ee4564a6344373d70b9fbd89a4638f2089738c3" } } ], "extra": [ 1, 173, 3, 234, 74, 119, 215, 229, 1, 205, 201, 3, 218, 231, 233, 251, 73, 41, 111, 10, 95, 50, 76, 142, 103, 244, 240, 99, 100, 177, 113, 234, 96, 2, 17, 0, 0, 0, 5, 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