Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7132f5199b1776c662b090c271e08cc8d0203ff0dfad49d9e9699c39e5aa13c

Tx prefix hash: ffcfe5d181e7354255c6d35a99fd3859b6b1a7496c82bc13e600141959f491b5
Tx public key: 26a0607632989d994bfc9a65273c7132dc71fe6ad8fa91629c9e7894117e2a6f
Timestamp: 1728967268 Timestamp [UCT]: 2024-10-15 04:41:08 Age [y:d:h:m:s]: 01:030:03:04:59
Block: 1131900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279910 RingCT/type: yes/0
Extra: 0126a0607632989d994bfc9a65273c7132dc71fe6ad8fa91629c9e7894117e2a6f021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a5a0fef81a221c23528ffb6e27b41e9519d66401c30e59f8431f2d3ad4a3266 0.600000000000 1614809 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": 1131910, "vin": [ { "gen": { "height": 1131900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a5a0fef81a221c23528ffb6e27b41e9519d66401c30e59f8431f2d3ad4a3266" } } ], "extra": [ 1, 38, 160, 96, 118, 50, 152, 157, 153, 75, 252, 154, 101, 39, 60, 113, 50, 220, 113, 254, 106, 216, 250, 145, 98, 156, 158, 120, 148, 17, 126, 42, 111, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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