Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0926a6ff79413cf243f423869d7d62e35ea77e6844f36fce094b303771dffc17

Tx prefix hash: bbffe6f645981812ae42ed4491f6a659f8c417afd91786c3145f67a2c6a3c116
Tx public key: 3e5d44439c71a6f626a86e350d229a253e774e925b4b1deb954438b3d3764eed
Timestamp: 1709710177 Timestamp [UCT]: 2024-03-06 07:29:37 Age [y:d:h:m:s]: 01:025:03:44:24
Block: 972256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278971 RingCT/type: yes/0
Extra: 013e5d44439c71a6f626a86e350d229a253e774e925b4b1deb954438b3d3764eed0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0de0a8f1e78b6f542e44d12b34f5156b224c277355407cdd858d1c767082201c 0.600000000000 1432165 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": 972266, "vin": [ { "gen": { "height": 972256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0de0a8f1e78b6f542e44d12b34f5156b224c277355407cdd858d1c767082201c" } } ], "extra": [ 1, 62, 93, 68, 67, 156, 113, 166, 246, 38, 168, 110, 53, 13, 34, 154, 37, 62, 119, 78, 146, 91, 75, 29, 235, 149, 68, 56, 179, 211, 118, 78, 237, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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