Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be4b7b74e5ea98af752bf6579343a5237bafcac44e2606151676fc92f2c37b1e

Tx prefix hash: 6c589249386adb6000092d8475114e6ce5fd59f5ff2fdd90c4615e9731d9fcea
Tx public key: a22b3756a401f0bb0cfe7c62934ba2438d841a958df0b8ca91c17e86701df497
Timestamp: 1713485467 Timestamp [UCT]: 2024-04-19 00:11:07 Age [y:d:h:m:s]: 00:352:13:25:36
Block: 1003535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252040 RingCT/type: yes/0
Extra: 01a22b3756a401f0bb0cfe7c62934ba2438d841a958df0b8ca91c17e86701df497021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b15fe20661a41615642aa706124f35e55df54d0ddc6550ff6785bf567a54e46 0.600000000000 1464077 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": 1003545, "vin": [ { "gen": { "height": 1003535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b15fe20661a41615642aa706124f35e55df54d0ddc6550ff6785bf567a54e46" } } ], "extra": [ 1, 162, 43, 55, 86, 164, 1, 240, 187, 12, 254, 124, 98, 147, 75, 162, 67, 141, 132, 26, 149, 141, 240, 184, 202, 145, 193, 126, 134, 112, 29, 244, 151, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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