Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bad27844c70ecf3391dc31da65f3e844969be8e6c5a11465ed0aaa2f9efad4e8

Tx prefix hash: 41e1d6dd7879efeae63bd8009dd4ac3bda42d3403124e264d192a12d23e8dcd3
Tx public key: 47b8e054ad953bb2e5aad83dc8cb303ddf270ac777b41a74faf4bf5ad91d2b56
Timestamp: 1693465334 Timestamp [UCT]: 2023-08-31 07:02:14 Age [y:d:h:m:s]: 01:077:05:19:28
Block: 837744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316494 RingCT/type: yes/0
Extra: 0147b8e054ad953bb2e5aad83dc8cb303ddf270ac777b41a74faf4bf5ad91d2b5602110000001d4b8f5122000000000000000000

1 output(s) for total of 1.028505074000 dcy

stealth address amount amount idx
00: 43c624e346abdcab50ca530480fda57660aa926f1623813e114140c0a6fb0c59 1.028505074000 1290402 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": 837754, "vin": [ { "gen": { "height": 837744 } } ], "vout": [ { "amount": 1028505074, "target": { "key": "43c624e346abdcab50ca530480fda57660aa926f1623813e114140c0a6fb0c59" } } ], "extra": [ 1, 71, 184, 224, 84, 173, 149, 59, 178, 229, 170, 216, 61, 200, 203, 48, 61, 223, 39, 10, 199, 119, 180, 26, 116, 250, 244, 191, 90, 217, 29, 43, 86, 2, 17, 0, 0, 0, 29, 75, 143, 81, 34, 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