Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 298e60885ee4d96b941a261d74d11101d9a09c0e01edf20797c31c43ca2ac0b3

Tx prefix hash: 98c899e67466b1db8f5d3c4bac5c722522e407301c0d9973665828627b42e77b
Tx public key: 74ff283f9117f7ec4d9c44ba24d534b2798693f7a4ae61ddf533268f1906f7b0
Timestamp: 1704379665 Timestamp [UCT]: 2024-01-04 14:47:45 Age [y:d:h:m:s]: 01:115:10:10:29
Block: 928057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343616 RingCT/type: yes/0
Extra: 0174ff283f9117f7ec4d9c44ba24d534b2798693f7a4ae61ddf533268f1906f7b0021100000001bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c48d8624076035a714d08c190ecda936d985c1a722d10d700adb5234e3f0ad68 0.600000000000 1385913 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": 928067, "vin": [ { "gen": { "height": 928057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c48d8624076035a714d08c190ecda936d985c1a722d10d700adb5234e3f0ad68" } } ], "extra": [ 1, 116, 255, 40, 63, 145, 23, 247, 236, 77, 156, 68, 186, 36, 213, 52, 178, 121, 134, 147, 247, 164, 174, 97, 221, 245, 51, 38, 143, 25, 6, 247, 176, 2, 17, 0, 0, 0, 1, 191, 162, 34, 33, 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