Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f913d7e13addb0bc9c0c4e34121a0e7d0eaceb4b40c583b6d11fcea94f0ffe2

Tx prefix hash: 77693ab9b5924444f3bee090d322f9ac3da2e5c307f2e8882e68450a6996815e
Tx public key: 50eef1b6eab7ddd33d2d0220c3b03872a6e55c472cf05b4e6446e7aa9e32a2e6
Timestamp: 1712044361 Timestamp [UCT]: 2024-04-02 07:52:41 Age [y:d:h:m:s]: 01:000:21:58:57
Block: 991569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261632 RingCT/type: yes/0
Extra: 0150eef1b6eab7ddd33d2d0220c3b03872a6e55c472cf05b4e6446e7aa9e32a2e602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9768a1a03dcb283818b472821138700ff4167dc11431047898b302bb8f418572 0.600000000000 1451905 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": 991579, "vin": [ { "gen": { "height": 991569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9768a1a03dcb283818b472821138700ff4167dc11431047898b302bb8f418572" } } ], "extra": [ 1, 80, 238, 241, 182, 234, 183, 221, 211, 61, 45, 2, 32, 195, 176, 56, 114, 166, 229, 92, 71, 44, 240, 91, 78, 100, 70, 231, 170, 158, 50, 162, 230, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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