Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f0b7fdca03b8173ce0cdc28b2aa4569a8300db8b1b8e9e69a24e8b47c5600ab

Tx prefix hash: 566abe54825dc69cd68f4c39e0c620a0395f2315b373d6f37fad58501efab963
Tx public key: e5a936a0a6fe31b6942194f7ec397c0c894f5a27500e54f616c45efa46d201e0
Timestamp: 1708293633 Timestamp [UCT]: 2024-02-18 22:00:33 Age [y:d:h:m:s]: 01:072:06:35:39
Block: 960511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312677 RingCT/type: yes/0
Extra: 01e5a936a0a6fe31b6942194f7ec397c0c894f5a27500e54f616c45efa46d201e002110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 288c6f2f85ab9ab99743b473a7aae3b7a20d181474c8e97a86d87ac8827ece6c 0.600000000000 1420082 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": 960521, "vin": [ { "gen": { "height": 960511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "288c6f2f85ab9ab99743b473a7aae3b7a20d181474c8e97a86d87ac8827ece6c" } } ], "extra": [ 1, 229, 169, 54, 160, 166, 254, 49, 182, 148, 33, 148, 247, 236, 57, 124, 12, 137, 79, 90, 39, 80, 14, 84, 246, 22, 196, 94, 250, 70, 210, 1, 224, 2, 17, 0, 0, 0, 11, 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