Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd6a1dc13cb6305be1a533c60b84bc196f8e4387008f4a3586539b3d4a283b88

Tx prefix hash: 9bd4f1d58079e97459a09dde96be41701fceffa77ac5f59213e63441431f1702
Tx public key: 6605eadb1d682e72b61cad3ec20e530a04674647ea52b49e6a95705b2fd1252b
Timestamp: 1681596445 Timestamp [UCT]: 2023-04-15 22:07:25 Age [y:d:h:m:s]: 01:272:07:37:01
Block: 739406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456130 RingCT/type: yes/0
Extra: 016605eadb1d682e72b61cad3ec20e530a04674647ea52b49e6a95705b2fd1252b0211000000015029cbac000000000000000000

1 output(s) for total of 2.177916367000 dcy

stealth address amount amount idx
00: b49f2a58b6e595072d11e34573c968e5a960f8ae5b13662f8ce760c19eff0216 2.177916367000 1186255 of 0

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": 739416, "vin": [ { "gen": { "height": 739406 } } ], "vout": [ { "amount": 2177916367, "target": { "key": "b49f2a58b6e595072d11e34573c968e5a960f8ae5b13662f8ce760c19eff0216" } } ], "extra": [ 1, 102, 5, 234, 219, 29, 104, 46, 114, 182, 28, 173, 62, 194, 14, 83, 10, 4, 103, 70, 71, 234, 82, 180, 158, 106, 149, 112, 91, 47, 209, 37, 43, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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