Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f536d996a5817e29efd1a10ac369060df1abdd7d091d61dce21b7477953a547

Tx prefix hash: bf47b4acfb0be785f287059288ae0de20966ab5d5f25b2ab84b8f0eda1e02086
Tx public key: 8e93821ef77f3be4b4587948d9184be55dd365d7cb673f830d2a301d928ae63b
Timestamp: 1730006145 Timestamp [UCT]: 2024-10-27 05:15:45 Age [y:d:h:m:s]: 00:143:05:35:05
Block: 1140470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102186 RingCT/type: yes/0
Extra: 018e93821ef77f3be4b4587948d9184be55dd365d7cb673f830d2a301d928ae63b021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29b5a4d47e09387a88e34a0f9c6b8025025cf42c6227ae553f575d3f4bc802ec 0.600000000000 1624269 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": 1140480, "vin": [ { "gen": { "height": 1140470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29b5a4d47e09387a88e34a0f9c6b8025025cf42c6227ae553f575d3f4bc802ec" } } ], "extra": [ 1, 142, 147, 130, 30, 247, 127, 59, 228, 180, 88, 121, 72, 217, 24, 75, 229, 93, 211, 101, 215, 203, 103, 63, 131, 13, 42, 48, 29, 146, 138, 230, 59, 2, 17, 0, 0, 0, 6, 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