Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 442fa81bcc8e8413cdf6894be48c8c3688787450d4dc1270a8724b6613258c9d

Tx prefix hash: 8a56ba8b9785996526dbbfcae4186b143abff60ba1a40e4abfd5344b4b271b52
Tx public key: 9ccf02ea540854bdecc4b5d476c4ec77c96e6e2ae81088e9bc4e8db5bddf5634
Timestamp: 1703503459 Timestamp [UCT]: 2023-12-25 11:24:19 Age [y:d:h:m:s]: 01:124:11:19:24
Block: 920790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350094 RingCT/type: yes/0
Extra: 019ccf02ea540854bdecc4b5d476c4ec77c96e6e2ae81088e9bc4e8db5bddf563402110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b96357d0069caf2ffb962577e4017fbea708b6206df9ba12a11cd21f2b47cba 0.600000000000 1378474 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": 920800, "vin": [ { "gen": { "height": 920790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b96357d0069caf2ffb962577e4017fbea708b6206df9ba12a11cd21f2b47cba" } } ], "extra": [ 1, 156, 207, 2, 234, 84, 8, 84, 189, 236, 196, 181, 212, 118, 196, 236, 119, 201, 110, 110, 42, 232, 16, 136, 233, 188, 78, 141, 181, 189, 223, 86, 52, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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