Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c059fd5ec8addec64fde2e951cc78ae6b6257cfa2d56576a7bf14a53b6fbed7

Tx prefix hash: 9b5391b8aa21921f9d8978d57a42288ea6e11bd3a38d3c1f1bcdda8a446897b4
Tx public key: bf1a622910173570b2e589f9d57ac1faa93b6ca5cc4e19ce5d9ce52c12f8f8f0
Timestamp: 1741916343 Timestamp [UCT]: 2025-03-14 01:39:03 Age [y:d:h:m:s]: 00:288:19:36:05
Block: 1238798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204196 RingCT/type: yes/0
Extra: 01bf1a622910173570b2e589f9d57ac1faa93b6ca5cc4e19ce5d9ce52c12f8f8f0021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 807709444abd1f928e24545eceb37dc6e5dfc68ac0c56b2fd0fc29f31d13e9f1 0.600000000000 1725759 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": 1238808, "vin": [ { "gen": { "height": 1238798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "807709444abd1f928e24545eceb37dc6e5dfc68ac0c56b2fd0fc29f31d13e9f1" } } ], "extra": [ 1, 191, 26, 98, 41, 16, 23, 53, 112, 178, 229, 137, 249, 213, 122, 193, 250, 169, 59, 108, 165, 204, 78, 25, 206, 93, 156, 229, 44, 18, 248, 248, 240, 2, 17, 0, 0, 0, 3, 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