Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 074871dacf4f1ecf03f946e44a0ca9e70427d5c2248ee9262318dcd96457f01e

Tx prefix hash: 22fdbbd6fce0a6a585c08b86c687db3670796c0444c9e87bad0440d3b54a02b8
Tx public key: 330ad07a84a110a42cc515977e477691d853c62c4be5ef2bd4efac0861246da2
Timestamp: 1636656000 Timestamp [UCT]: 2021-11-11 18:40:00 Age [y:d:h:m:s]: 03:054:05:26:26
Block: 372280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 817378 RingCT/type: yes/0
Extra: 01330ad07a84a110a42cc515977e477691d853c62c4be5ef2bd4efac0861246da202110000001c1154028c000000000000000000

1 output(s) for total of 35.849426312000 dcy

stealth address amount amount idx
00: 0a711a564d5aa8ddafa4fd1c17f32ca52c2a5adb3629c6d726e6844dde5038df 35.849426312000 754164 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": 372290, "vin": [ { "gen": { "height": 372280 } } ], "vout": [ { "amount": 35849426312, "target": { "key": "0a711a564d5aa8ddafa4fd1c17f32ca52c2a5adb3629c6d726e6844dde5038df" } } ], "extra": [ 1, 51, 10, 208, 122, 132, 161, 16, 164, 44, 197, 21, 151, 126, 71, 118, 145, 216, 83, 198, 44, 75, 229, 239, 43, 212, 239, 172, 8, 97, 36, 109, 162, 2, 17, 0, 0, 0, 28, 17, 84, 2, 140, 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