Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d64e85f997d589744bb631e762084ebc344c6463c53b90bb29357374bddd2b9

Tx prefix hash: 849514171f782b178eb1edbe3d7cab1d05193c311a79fd8240447bec3bb1cc26
Tx public key: 0c11baed0e227eb0d6e4f5cbeec9b5fafa8ad948a02d89e6b7d0f0c9aa0cbf83
Timestamp: 1724088026 Timestamp [UCT]: 2024-08-19 17:20:26 Age [y:d:h:m:s]: 00:292:23:29:13
Block: 1091451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209308 RingCT/type: yes/0
Extra: 010c11baed0e227eb0d6e4f5cbeec9b5fafa8ad948a02d89e6b7d0f0c9aa0cbf8302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d5e830cf43d5354276af8cb372a02c22f2bfe7b4af09ce4d2652235b77b6208 0.600000000000 1566084 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": 1091461, "vin": [ { "gen": { "height": 1091451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d5e830cf43d5354276af8cb372a02c22f2bfe7b4af09ce4d2652235b77b6208" } } ], "extra": [ 1, 12, 17, 186, 237, 14, 34, 126, 176, 214, 228, 245, 203, 238, 201, 181, 250, 250, 138, 217, 72, 160, 45, 137, 230, 183, 208, 240, 201, 170, 12, 191, 131, 2, 17, 0, 0, 0, 1, 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