Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6dc98c81ba3a6d2b468f601b4eb3a4b2a3fe35fe557911424238c526002111c

Tx prefix hash: 967bd01d35ba2b168bd76d5fc4327d7a4f3d0bc0dc5d32db35fd51e29573b471
Tx public key: 4ff6808d58074cf8a7649accbeb785703092c5191f5749c4c47a5c7f578baae6
Timestamp: 1717569399 Timestamp [UCT]: 2024-06-05 06:36:39 Age [y:d:h:m:s]: 00:309:22:17:24
Block: 1037415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221497 RingCT/type: yes/0
Extra: 014ff6808d58074cf8a7649accbeb785703092c5191f5749c4c47a5c7f578baae602110000001159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6e08c37342935d4a87fae4ffdaede8fc23d9f3163be89dd20a8b9834b44c569 0.600000000000 1505946 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": 1037425, "vin": [ { "gen": { "height": 1037415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6e08c37342935d4a87fae4ffdaede8fc23d9f3163be89dd20a8b9834b44c569" } } ], "extra": [ 1, 79, 246, 128, 141, 88, 7, 76, 248, 167, 100, 154, 204, 190, 183, 133, 112, 48, 146, 197, 25, 31, 87, 73, 196, 196, 122, 92, 127, 87, 139, 170, 230, 2, 17, 0, 0, 0, 17, 89, 218, 211, 245, 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