Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8994d937ca82295b57ebf390e95b92577fa8e8d48cf7aa0c8333b61aa6169a39

Tx prefix hash: 27f80bdd81b18c360aef3c001dd0c5d465219ef5061de3d70e8f7e87bd718f73
Tx public key: 765949b374cb66039669441b570dcd961b312f7c0e0721a8e8964802d42da332
Timestamp: 1628755699 Timestamp [UCT]: 2021-08-12 08:08:19 Age [y:d:h:m:s]: 03:108:12:29:13
Block: 312321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 850752 RingCT/type: yes/0
Extra: 01765949b374cb66039669441b570dcd961b312f7c0e0721a8e8964802d42da33202110000003ea272b9cb000000000000000000

1 output(s) for total of 56.644645417000 dcy

stealth address amount amount idx
00: 956a23bff1142edb6871512d1dccf440c3ad7b8b3a38d3d5e7a88f80cdbf2355 56.644645417000 649838 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": 312331, "vin": [ { "gen": { "height": 312321 } } ], "vout": [ { "amount": 56644645417, "target": { "key": "956a23bff1142edb6871512d1dccf440c3ad7b8b3a38d3d5e7a88f80cdbf2355" } } ], "extra": [ 1, 118, 89, 73, 179, 116, 203, 102, 3, 150, 105, 68, 27, 87, 13, 205, 150, 27, 49, 47, 124, 14, 7, 33, 168, 232, 150, 72, 2, 212, 45, 163, 50, 2, 17, 0, 0, 0, 62, 162, 114, 185, 203, 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