Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9e85f275955ad22c6bbf8140b9b21c28ace87888f6c59a64f5882f52e65ad77

Tx prefix hash: 723d384a4ce617a5c9f66804b3fa83da1032081e8df52c6a4469f5959c9a9864
Tx public key: 46827c9b1d33d6d4f313dda8a3a4b1207820281422199f745ba2b0918ba8e134
Timestamp: 1736548263 Timestamp [UCT]: 2025-01-10 22:31:03 Age [y:d:h:m:s]: 00:070:22:56:45
Block: 1194606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50500 RingCT/type: yes/0
Extra: 0146827c9b1d33d6d4f313dda8a3a4b1207820281422199f745ba2b0918ba8e134021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79d70282e9dcc9ad686423c7753a745a26ae52141f3ba6cceed9f932ed08f9fd 0.600000000000 1681183 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": 1194616, "vin": [ { "gen": { "height": 1194606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79d70282e9dcc9ad686423c7753a745a26ae52141f3ba6cceed9f932ed08f9fd" } } ], "extra": [ 1, 70, 130, 124, 155, 29, 51, 214, 212, 243, 19, 221, 168, 163, 164, 177, 32, 120, 32, 40, 20, 34, 25, 159, 116, 91, 162, 176, 145, 139, 168, 225, 52, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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