Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6331ac19cc5c379eb3003dcfca2ab1c5dd5fec19c42d879de3340c9d5930e722

Tx prefix hash: beeb594379e7827d654d552aed2f1bbd6e154e1a3161737ba83c95d35d64ce88
Tx public key: 5d892aadfdd5868c7a2e22a2e94f31f7aee0a6bad1c25c6d927a52d6e5503e1a
Timestamp: 1681760212 Timestamp [UCT]: 2023-04-17 19:36:52 Age [y:d:h:m:s]: 01:312:18:49:28
Block: 740766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484787 RingCT/type: yes/0
Extra: 015d892aadfdd5868c7a2e22a2e94f31f7aee0a6bad1c25c6d927a52d6e5503e1a021100000001e6d27f9c000000000000000000

1 output(s) for total of 2.155435106000 dcy

stealth address amount amount idx
00: 8001ceaaf99ec40f273e38bbbea54b0a4db041a3f5bcea1e7a5d4eb1494a8f9f 2.155435106000 1187671 of 0

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": 740776, "vin": [ { "gen": { "height": 740766 } } ], "vout": [ { "amount": 2155435106, "target": { "key": "8001ceaaf99ec40f273e38bbbea54b0a4db041a3f5bcea1e7a5d4eb1494a8f9f" } } ], "extra": [ 1, 93, 137, 42, 173, 253, 213, 134, 140, 122, 46, 34, 162, 233, 79, 49, 247, 174, 224, 166, 186, 209, 194, 92, 109, 146, 122, 82, 214, 229, 80, 62, 26, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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