Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87a93e4c8270d1e6cef511d5de4287f37a8bd8c2357032573d773448b24d924c

Tx prefix hash: 4c33ae8eab006f92d0db552b742212727d6940a169c54e1b4a6eb58557974c5b
Tx public key: 0e6d3b82fddda3b3031c9b500bfd674300094e40e855eaaf8be48e18c842a679
Timestamp: 1736989974 Timestamp [UCT]: 2025-01-16 01:12:54 Age [y:d:h:m:s]: 00:152:18:52:57
Block: 1198259 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108912 RingCT/type: yes/0
Extra: 010e6d3b82fddda3b3031c9b500bfd674300094e40e855eaaf8be48e18c842a679021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c62c4043554138d0c21048d1d566c0fcd1237c3c790714a6ac1e4151e2c0384 0.600000000000 1684880 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": 1198269, "vin": [ { "gen": { "height": 1198259 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c62c4043554138d0c21048d1d566c0fcd1237c3c790714a6ac1e4151e2c0384" } } ], "extra": [ 1, 14, 109, 59, 130, 253, 221, 163, 179, 3, 28, 155, 80, 11, 253, 103, 67, 0, 9, 78, 64, 232, 85, 234, 175, 139, 228, 142, 24, 200, 66, 166, 121, 2, 17, 0, 0, 0, 4, 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