Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5f2e4024ad9335adbf473767ecef193ad4ec6bade2eaae7fa21f75ccb54dcb8

Tx prefix hash: 6e88e6f5cdedd80204c57d59f46df3e7be186aad058c4aba5e59d98a79d797c7
Tx public key: a281b81f29973b6e9471e925c6b03b647f0cf45afa4c1249501b57c0d241e890
Timestamp: 1723224149 Timestamp [UCT]: 2024-08-09 17:22:29 Age [y:d:h:m:s]: 00:167:05:02:50
Block: 1084291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119569 RingCT/type: yes/0
Extra: 01a281b81f29973b6e9471e925c6b03b647f0cf45afa4c1249501b57c0d241e89002110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec28ca457347ece98a1320029ce84a4d5c1048a2d8ec7d64098ef78ef8c93315 0.600000000000 1558512 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": 1084301, "vin": [ { "gen": { "height": 1084291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec28ca457347ece98a1320029ce84a4d5c1048a2d8ec7d64098ef78ef8c93315" } } ], "extra": [ 1, 162, 129, 184, 31, 41, 151, 59, 110, 148, 113, 233, 37, 198, 176, 59, 100, 127, 12, 244, 90, 250, 76, 18, 73, 80, 27, 87, 192, 210, 65, 232, 144, 2, 17, 0, 0, 0, 2, 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