Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c985058cd7ba6aab6d9f34dcbadee728b17156322d5b29da41a5b159d17b3d19

Tx prefix hash: e1e0e467137392ecefa2a6964c1140967d1baf963b28b275ada8b962d0b63691
Tx public key: 1e1ff64f8d2e668746148d36075a20af754b630784824b4ae40c499ae8d56af9
Timestamp: 1744657091 Timestamp [UCT]: 2025-04-14 18:58:11 Age [y:d:h:m:s]: 00:253:06:57:55
Block: 1261465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178797 RingCT/type: yes/0
Extra: 011e1ff64f8d2e668746148d36075a20af754b630784824b4ae40c499ae8d56af90211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9545405391d932b6f9aa76c0108bf7b3fe3a27e7715a57173abee8a43d3037a3 0.600000000000 1748636 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": 1261475, "vin": [ { "gen": { "height": 1261465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9545405391d932b6f9aa76c0108bf7b3fe3a27e7715a57173abee8a43d3037a3" } } ], "extra": [ 1, 30, 31, 246, 79, 141, 46, 102, 135, 70, 20, 141, 54, 7, 90, 32, 175, 117, 75, 99, 7, 132, 130, 75, 74, 228, 12, 73, 154, 232, 213, 106, 249, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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