Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05c97ddc959aa125d5d2d3d5dfb969a7d941932c80c562c7bd01b77c234bafcc

Tx prefix hash: a07fd8c316fbf6149e81ea417232d2d4b7270dc24447fb1fa969488db140c9ce
Tx public key: 0915277635851071c8167038c5120a8b8a841df232a1e418dbb1ef3345d6ce84
Timestamp: 1745826160 Timestamp [UCT]: 2025-04-28 07:42:40 Age [y:d:h:m:s]: 00:206:14:39:17
Block: 1271150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145379 RingCT/type: yes/0
Extra: 010915277635851071c8167038c5120a8b8a841df232a1e418dbb1ef3345d6ce8402110000000c9f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cc7007ddeed27a9a260cb5c2102a6fbb6a46dfb35e6c097746bec402eeace14 0.600000000000 1758403 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": 1271160, "vin": [ { "gen": { "height": 1271150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cc7007ddeed27a9a260cb5c2102a6fbb6a46dfb35e6c097746bec402eeace14" } } ], "extra": [ 1, 9, 21, 39, 118, 53, 133, 16, 113, 200, 22, 112, 56, 197, 18, 10, 139, 138, 132, 29, 242, 50, 161, 228, 24, 219, 177, 239, 51, 69, 214, 206, 132, 2, 17, 0, 0, 0, 12, 159, 159, 230, 140, 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