Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14044fafe99568f4f4bc2b0fa641012af33bf7aea758a250dbb4950a30b231df

Tx prefix hash: 4f6f082a0b2429a24ecd91fb146f71740c35ac63bcafb6bc8d0b51e45757c1a3
Tx public key: 94f82ba8ff0b119f1216a6fa452035aed499ebca6b00f7e9d15daa2b986fa5a8
Timestamp: 1706666748 Timestamp [UCT]: 2024-01-31 02:05:48 Age [y:d:h:m:s]: 01:060:14:30:51
Block: 946994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304382 RingCT/type: yes/0
Extra: 0194f82ba8ff0b119f1216a6fa452035aed499ebca6b00f7e9d15daa2b986fa5a80211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e643763653a0e16c492017624e23cc232b6d41be8ced7f5450ad50c854065f17 0.600000000000 1405340 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": 947004, "vin": [ { "gen": { "height": 946994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e643763653a0e16c492017624e23cc232b6d41be8ced7f5450ad50c854065f17" } } ], "extra": [ 1, 148, 248, 43, 168, 255, 11, 17, 159, 18, 22, 166, 250, 69, 32, 53, 174, 212, 153, 235, 202, 107, 0, 247, 233, 209, 93, 170, 43, 152, 111, 165, 168, 2, 17, 0, 0, 0, 2, 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