Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37924e251c26ad1e81443a0ab3bd2fcc08e4e3d28bca49d7840fe7c00f166a19

Tx prefix hash: bc077e53d199025ded02a7801b139b48f94934285d274e8b289d7f9ee2de3e3c
Tx public key: ae42ec981868e185703c08ecf8e124000e87ab0c4dccc40774e7573ea855aba3
Timestamp: 1607639731 Timestamp [UCT]: 2020-12-10 22:35:31 Age [y:d:h:m:s]: 04:138:13:42:16
Block: 159754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1110825 RingCT/type: yes/0
Extra: 01ae42ec981868e185703c08ecf8e124000e87ab0c4dccc40774e7573ea855aba3021100000009b9b01d0b000000000000000000

1 output(s) for total of 181.413399553000 dcy

stealth address amount amount idx
00: 02a066a5114dfe0ae1b8e208023a79b488ae574a647bbe871fdce3a0ff78e7d9 181.413399553000 280069 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": 159764, "vin": [ { "gen": { "height": 159754 } } ], "vout": [ { "amount": 181413399553, "target": { "key": "02a066a5114dfe0ae1b8e208023a79b488ae574a647bbe871fdce3a0ff78e7d9" } } ], "extra": [ 1, 174, 66, 236, 152, 24, 104, 225, 133, 112, 60, 8, 236, 248, 225, 36, 0, 14, 135, 171, 12, 77, 204, 196, 7, 116, 231, 87, 62, 168, 85, 171, 163, 2, 17, 0, 0, 0, 9, 185, 176, 29, 11, 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