Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1496e043d00389606ca54e793e7936e1cb567d8c36357c8c0d132e5a651cb190

Tx prefix hash: c952a25aed65eb71d57a09f2e9ac699f9b6afd84bbb9ddc3c14be4592720fdce
Tx public key: 6cb1b9ad43518a23da329199132fe91621d189cb458d2b75df0106c228ec2d0b
Timestamp: 1702689924 Timestamp [UCT]: 2023-12-16 01:25:24 Age [y:d:h:m:s]: 01:188:22:01:08
Block: 914046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396011 RingCT/type: yes/0
Extra: 016cb1b9ad43518a23da329199132fe91621d189cb458d2b75df0106c228ec2d0b021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ef518c71ca4a5bbfbafd9e909320eb412c24312119604934309c45cd8e82178 0.600000000000 1371328 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": 914056, "vin": [ { "gen": { "height": 914046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ef518c71ca4a5bbfbafd9e909320eb412c24312119604934309c45cd8e82178" } } ], "extra": [ 1, 108, 177, 185, 173, 67, 81, 138, 35, 218, 50, 145, 153, 19, 47, 233, 22, 33, 209, 137, 203, 69, 141, 43, 117, 223, 1, 6, 194, 40, 236, 45, 11, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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