Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b1a3f91798684bb3912d1883608e460a41976d5efa11d3de0d701b0c2893fcb

Tx prefix hash: 26598333dfa440fd5728544e8a91bfc0003ddd0df5abfe498b9186f6ef62c14d
Tx public key: 0afa6c22a86fa3d0c73032b53e0b2004959e5f654743e326a1c9a3c76d1655f2
Timestamp: 1736050203 Timestamp [UCT]: 2025-01-05 04:10:03 Age [y:d:h:m:s]: 00:165:10:34:43
Block: 1190495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117939 RingCT/type: yes/0
Extra: 010afa6c22a86fa3d0c73032b53e0b2004959e5f654743e326a1c9a3c76d1655f2021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b38656dc646a87932688123c47e933510ad8a92fcf5b2e30a44d1211d270bb20 0.600000000000 1677012 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": 1190505, "vin": [ { "gen": { "height": 1190495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b38656dc646a87932688123c47e933510ad8a92fcf5b2e30a44d1211d270bb20" } } ], "extra": [ 1, 10, 250, 108, 34, 168, 111, 163, 208, 199, 48, 50, 181, 62, 11, 32, 4, 149, 158, 95, 101, 71, 67, 227, 38, 161, 201, 163, 199, 109, 22, 85, 242, 2, 17, 0, 0, 0, 5, 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