Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7954b31ce20616bb05d55ac83862cb7252f4fde4eeb094b8386fdd81923150d7

Tx prefix hash: 306368c2e8c57561930c20e1dcd4fd30df564651abf272f08ec4ed7b1afbeca2
Tx public key: d451c75b0527e41d9392ef749aae797f672858b969b8c17daa2ac42bb8e5f020
Timestamp: 1722083225 Timestamp [UCT]: 2024-07-27 12:27:05 Age [y:d:h:m:s]: 00:265:05:26:19
Block: 1074832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189471 RingCT/type: yes/0
Extra: 01d451c75b0527e41d9392ef749aae797f672858b969b8c17daa2ac42bb8e5f020021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e50a51d9fe83bedd5f9dbe2304a7d49a62aed2b4ca69019b27a20df8cc1e77a 0.600000000000 1547351 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": 1074842, "vin": [ { "gen": { "height": 1074832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e50a51d9fe83bedd5f9dbe2304a7d49a62aed2b4ca69019b27a20df8cc1e77a" } } ], "extra": [ 1, 212, 81, 199, 91, 5, 39, 228, 29, 147, 146, 239, 116, 154, 174, 121, 127, 103, 40, 88, 185, 105, 184, 193, 125, 170, 42, 196, 43, 184, 229, 240, 32, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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