Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c059bfadf3b7914285a759d29d3ce8f2004db3b4e589a823aecb10d5639fb6fa

Tx prefix hash: 97649c334379597a307d07da658f2bc54645b82bcae44fd2bb7049dc3640de7b
Tx public key: 4e6e6ce75939202f3da4e6f177ca78a61e18e7f3041cbe86dbcda965733bc0a7
Timestamp: 1709095918 Timestamp [UCT]: 2024-02-28 04:51:58 Age [y:d:h:m:s]: 01:254:21:57:45
Block: 967160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440912 RingCT/type: yes/0
Extra: 014e6e6ce75939202f3da4e6f177ca78a61e18e7f3041cbe86dbcda965733bc0a70211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8eb2b8539baf29e11c0f380a7737d917a097f8d85b9f47ebff34fe19a85ae1d3 0.600000000000 1426931 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": 967170, "vin": [ { "gen": { "height": 967160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8eb2b8539baf29e11c0f380a7737d917a097f8d85b9f47ebff34fe19a85ae1d3" } } ], "extra": [ 1, 78, 110, 108, 231, 89, 57, 32, 47, 61, 164, 230, 241, 119, 202, 120, 166, 30, 24, 231, 243, 4, 28, 190, 134, 219, 205, 169, 101, 115, 59, 192, 167, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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