Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fe9926e72b5d318d9ba6942c295db5b328e243bed37d660c784a32d6c0c8ed2

Tx prefix hash: e3a6c3cd752f80584617ca938067d8fb40a1c24c078746243d8cbd968b91b1f4
Tx public key: 5a71e2859f0089cda8efc7d37026757b512721fb1baa78eccef9dd2878bf1844
Timestamp: 1708308746 Timestamp [UCT]: 2024-02-19 02:12:26 Age [y:d:h:m:s]: 01:274:18:25:51
Block: 960629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455138 RingCT/type: yes/0
Extra: 015a71e2859f0089cda8efc7d37026757b512721fb1baa78eccef9dd2878bf184402110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25973b50a61feaad7ee29585c4a28cc889c6b4a4800c03562dfe396641e65097 0.600000000000 1420214 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": 960639, "vin": [ { "gen": { "height": 960629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25973b50a61feaad7ee29585c4a28cc889c6b4a4800c03562dfe396641e65097" } } ], "extra": [ 1, 90, 113, 226, 133, 159, 0, 137, 205, 168, 239, 199, 211, 112, 38, 117, 123, 81, 39, 33, 251, 27, 170, 120, 236, 206, 249, 221, 40, 120, 191, 24, 68, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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