Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46d611033478918ed53662ad1d5bb37569bbe5b5f103451700de087cd29404ce

Tx prefix hash: 40a45ef3f9e1938519ff2c5306c4fbfc234bf9cfd09d7c4abd70cdd22beebb03
Tx public key: 2d17416efc1d4b7ca7777c1f97e91da2d682cc4d48759af0f27a912eac27f70b
Timestamp: 1699401789 Timestamp [UCT]: 2023-11-08 00:03:09 Age [y:d:h:m:s]: 01:154:15:28:24
Block: 886786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371720 RingCT/type: yes/0
Extra: 012d17416efc1d4b7ca7777c1f97e91da2d682cc4d48759af0f27a912eac27f70b0211000000014b8f5122000000000000000000

1 output(s) for total of 0.707472987000 dcy

stealth address amount amount idx
00: 19b3062ada0e4d60b0054c737bdbb8a97aa5533e59cfc05dd61cc6ea41c6a97d 0.707472987000 1342629 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": 886796, "vin": [ { "gen": { "height": 886786 } } ], "vout": [ { "amount": 707472987, "target": { "key": "19b3062ada0e4d60b0054c737bdbb8a97aa5533e59cfc05dd61cc6ea41c6a97d" } } ], "extra": [ 1, 45, 23, 65, 110, 252, 29, 75, 124, 167, 119, 124, 31, 151, 233, 29, 162, 214, 130, 204, 77, 72, 117, 154, 240, 242, 122, 145, 46, 172, 39, 247, 11, 2, 17, 0, 0, 0, 1, 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