Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2db90d8015c54c1a7fcdeea78bd7108e14252003f42aab1d950cd22c5cb064e

Tx prefix hash: 31211dfaf9cfb1c47168c36c4a7b18d75efc574d239058b1d23616a61f9c78bc
Tx public key: 79b4fcdfb15ffd7830f04bdd6c7ac4c3311ca418495e10791d8f13151b1d3a52
Timestamp: 1730185583 Timestamp [UCT]: 2024-10-29 07:06:23 Age [y:d:h:m:s]: 00:179:11:44:29
Block: 1141939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128124 RingCT/type: yes/0
Extra: 0179b4fcdfb15ffd7830f04bdd6c7ac4c3311ca418495e10791d8f13151b1d3a52021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efa9106df4f008553bbb455831a1b25df1327b7e752c99bfe1688b7cb6a12833 0.600000000000 1625772 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": 1141949, "vin": [ { "gen": { "height": 1141939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efa9106df4f008553bbb455831a1b25df1327b7e752c99bfe1688b7cb6a12833" } } ], "extra": [ 1, 121, 180, 252, 223, 177, 95, 253, 120, 48, 240, 75, 221, 108, 122, 196, 195, 49, 28, 164, 24, 73, 94, 16, 121, 29, 143, 19, 21, 27, 29, 58, 82, 2, 17, 0, 0, 0, 2, 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