Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c90075fab4f80fde1f21162bb237c37d587083e04b7a2491648cff5f68e2614

Tx prefix hash: 8dbdee3f615c50786efce7a7db24bf0298342a7c17ac37068a43831ddbd91258
Tx public key: 73255e6a034dad265a9d4bb09c5c3d2176b335ed6ec9bc53a29b182ef74e82f0
Timestamp: 1735602143 Timestamp [UCT]: 2024-12-30 23:42:23 Age [y:d:h:m:s]: 00:094:02:04:14
Block: 1186767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67027 RingCT/type: yes/0
Extra: 0173255e6a034dad265a9d4bb09c5c3d2176b335ed6ec9bc53a29b182ef74e82f0021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19e3480db44f0096e7658ddfe081b2427cb66f94ac2320dc517e1d42f45cb8fc 0.600000000000 1673252 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": 1186777, "vin": [ { "gen": { "height": 1186767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19e3480db44f0096e7658ddfe081b2427cb66f94ac2320dc517e1d42f45cb8fc" } } ], "extra": [ 1, 115, 37, 94, 106, 3, 77, 173, 38, 90, 157, 75, 176, 156, 92, 61, 33, 118, 179, 53, 237, 110, 201, 188, 83, 162, 155, 24, 46, 247, 78, 130, 240, 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