Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93614ea5c363f6fee196d2d20231a18f4aaa2daacbf479d9b60e62a708702262

Tx prefix hash: 5a420206e51612064128f5ffe8cd8bb79a224b0bd5136c6240bdad3f9b2c2f11
Tx public key: 6536cce19af9fa737c7a9b7edec59e6f862b2a5adf7de1d1137b07f6dcf435a3
Timestamp: 1745582653 Timestamp [UCT]: 2025-04-25 12:04:13 Age [y:d:h:m:s]: 00:257:00:08:45
Block: 1269137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181470 RingCT/type: yes/0
Extra: 016536cce19af9fa737c7a9b7edec59e6f862b2a5adf7de1d1137b07f6dcf435a3021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c596930763394cacc5256845989b3c8a13bc86e190a81cab6f6935f99a288d3 0.600000000000 1756372 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": 1269147, "vin": [ { "gen": { "height": 1269137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c596930763394cacc5256845989b3c8a13bc86e190a81cab6f6935f99a288d3" } } ], "extra": [ 1, 101, 54, 204, 225, 154, 249, 250, 115, 124, 122, 155, 126, 222, 197, 158, 111, 134, 43, 42, 90, 223, 125, 225, 209, 19, 123, 7, 246, 220, 244, 53, 163, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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