Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70cc28f38d8a1e894a7e5bc18d9f24570dd0f9a78438f8f39663273876293f0d

Tx prefix hash: 08f1a99e2141d6a0baa8c9ceeb8d130ef44c5f86a3d94db06a95f3fa19cbf7c7
Tx public key: 975714d72883f8918c3efa7129383e268ebffa32f68880b5c03ad1639b5740ff
Timestamp: 1721715896 Timestamp [UCT]: 2024-07-23 06:24:56 Age [y:d:h:m:s]: 00:275:09:22:20
Block: 1071766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196765 RingCT/type: yes/0
Extra: 01975714d72883f8918c3efa7129383e268ebffa32f68880b5c03ad1639b5740ff02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2990baa47054baee5024f2f479df1dda0c734a6a85aa9bfd5b599b79fa25b37c 0.600000000000 1544117 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": 1071776, "vin": [ { "gen": { "height": 1071766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2990baa47054baee5024f2f479df1dda0c734a6a85aa9bfd5b599b79fa25b37c" } } ], "extra": [ 1, 151, 87, 20, 215, 40, 131, 248, 145, 140, 62, 250, 113, 41, 56, 62, 38, 142, 191, 250, 50, 246, 136, 128, 181, 192, 58, 209, 99, 155, 87, 64, 255, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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