Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0aecb20c024e4e4a810a33f1ae62b16fa22c7f5971e33758bf0bbdbb9fb2de01

Tx prefix hash: 789b9bb0c2f3149952e39ac2d14e408eb3bfcf0794ea5bfef98c856e1e38c3ca
Tx public key: af1d4726e625bf66c614130c5e7b5e97a9b2d5bb00621c33e856633c626d2e13
Timestamp: 1728061269 Timestamp [UCT]: 2024-10-04 17:01:09 Age [y:d:h:m:s]: 00:054:17:30:04
Block: 1124398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39095 RingCT/type: yes/0
Extra: 01af1d4726e625bf66c614130c5e7b5e97a9b2d5bb00621c33e856633c626d2e1302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41d241ce7f202465a05a4b0a726b996470dcc9a28dcf478a1c9819550ba614d8 0.600000000000 1607017 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": 1124408, "vin": [ { "gen": { "height": 1124398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41d241ce7f202465a05a4b0a726b996470dcc9a28dcf478a1c9819550ba614d8" } } ], "extra": [ 1, 175, 29, 71, 38, 230, 37, 191, 102, 198, 20, 19, 12, 94, 123, 94, 151, 169, 178, 213, 187, 0, 98, 28, 51, 232, 86, 99, 60, 98, 109, 46, 19, 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