Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9554a4d698b9c50519e84628d0f233417f0488a0cfa6db297f73e8252c97853d

Tx prefix hash: e03762479db7be8112c963cb849db84fa59c2b2250e1427a227f712b8b5655b4
Tx public key: f5a2c1dea970b3caa48cf846cfe2822e931bb8ad10077cf6fadf3ecc1cb14465
Timestamp: 1703436988 Timestamp [UCT]: 2023-12-24 16:56:28 Age [y:d:h:m:s]: 01:322:11:47:26
Block: 920243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489316 RingCT/type: yes/0
Extra: 01f5a2c1dea970b3caa48cf846cfe2822e931bb8ad10077cf6fadf3ecc1cb1446502110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6417eff743507307d5223adacaa7125bb9db7850d45e3e4c3b71713423c076b2 0.600000000000 1377921 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": 920253, "vin": [ { "gen": { "height": 920243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6417eff743507307d5223adacaa7125bb9db7850d45e3e4c3b71713423c076b2" } } ], "extra": [ 1, 245, 162, 193, 222, 169, 112, 179, 202, 164, 140, 248, 70, 207, 226, 130, 46, 147, 27, 184, 173, 16, 7, 124, 246, 250, 223, 62, 204, 28, 177, 68, 101, 2, 17, 0, 0, 0, 9, 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