Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b0411155db731aef396c38bc766cb0f81417cd307182f4f38e9c400a5f6de28

Tx prefix hash: 8bd68c10554ef32b5c9c4dcde44995e0f6c74cb7accc1067b2ce3817f126d2ce
Tx public key: 65e5963d7e0da4d852241eb121e0b0af136771a2b68a3b3fb04fa86615ad7c62
Timestamp: 1734374237 Timestamp [UCT]: 2024-12-16 18:37:17 Age [y:d:h:m:s]: 00:131:00:44:11
Block: 1176629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93448 RingCT/type: yes/0
Extra: 0165e5963d7e0da4d852241eb121e0b0af136771a2b68a3b3fb04fa86615ad7c62021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 188e98b8b22ae9ac4aa662272db762d869a996a322ddc6b250c3481dc447ab00 0.600000000000 1662982 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": 1176639, "vin": [ { "gen": { "height": 1176629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "188e98b8b22ae9ac4aa662272db762d869a996a322ddc6b250c3481dc447ab00" } } ], "extra": [ 1, 101, 229, 150, 61, 126, 13, 164, 216, 82, 36, 30, 177, 33, 224, 176, 175, 19, 103, 113, 162, 182, 138, 59, 63, 176, 79, 168, 102, 21, 173, 124, 98, 2, 17, 0, 0, 0, 3, 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