Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e0ff39e49c4abd2944814415207e2df09939216e03acd08e3058a52900c6cef

Tx prefix hash: 9d02cfd6e40f6e8b329e6508afed75be598d678229cd9e30332a20f939fa83cb
Tx public key: 6a8aa3efd08096fd83d12c59094378a07c5ef7b96eda9f2c1f8971ac8bc863da
Timestamp: 1711572722 Timestamp [UCT]: 2024-03-27 20:52:02 Age [y:d:h:m:s]: 01:020:01:40:49
Block: 987700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275302 RingCT/type: yes/0
Extra: 016a8aa3efd08096fd83d12c59094378a07c5ef7b96eda9f2c1f8971ac8bc863da02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f336698ca546450e8151e0f3c1da5f87b2cba38d51bf52aaca97c68b8e70863 0.600000000000 1447957 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": 987710, "vin": [ { "gen": { "height": 987700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f336698ca546450e8151e0f3c1da5f87b2cba38d51bf52aaca97c68b8e70863" } } ], "extra": [ 1, 106, 138, 163, 239, 208, 128, 150, 253, 131, 209, 44, 89, 9, 67, 120, 160, 124, 94, 247, 185, 110, 218, 159, 44, 31, 137, 113, 172, 139, 200, 99, 218, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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