Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d76b75f0822ca6241e7272a4306059827d21639e7412d46e39d9ad4e95dc8775

Tx prefix hash: eba829965b13421d646b352788ea7ffcea1d3248bb77ec151833ff004c95613c
Tx public key: c7aa21af9bcf5de856c92e53d886c1083c7b0ee7d8bdb03cd80a55e6481091c1
Timestamp: 1706218095 Timestamp [UCT]: 2024-01-25 21:28:15 Age [y:d:h:m:s]: 01:346:04:38:58
Block: 943268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506321 RingCT/type: yes/0
Extra: 01c7aa21af9bcf5de856c92e53d886c1083c7b0ee7d8bdb03cd80a55e6481091c102110000001352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c67c5b3b8e3bb63db25b85802aa6776f3f5f2ab51eef569d988ba7505a3d7d6 0.600000000000 1401472 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": 943278, "vin": [ { "gen": { "height": 943268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c67c5b3b8e3bb63db25b85802aa6776f3f5f2ab51eef569d988ba7505a3d7d6" } } ], "extra": [ 1, 199, 170, 33, 175, 155, 207, 93, 232, 86, 201, 46, 83, 216, 134, 193, 8, 60, 123, 14, 231, 216, 189, 176, 60, 216, 10, 85, 230, 72, 16, 145, 193, 2, 17, 0, 0, 0, 19, 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