Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc90c4829c25c262fea50a005cf304bc7ec8ffd4354850b6bde01233acb7b755

Tx prefix hash: 8d4c0151ddccf58cd38af88dafe4575c35e0ccf1d4fba9d901231c5bdd278cbb
Tx public key: aa397a60b02e32f643295fc65e44ccea8179d14878259d0a7f7643d5d4606b7a
Timestamp: 1719295215 Timestamp [UCT]: 2024-06-25 06:00:15 Age [y:d:h:m:s]: 00:288:05:56:09
Block: 1051708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205980 RingCT/type: yes/0
Extra: 01aa397a60b02e32f643295fc65e44ccea8179d14878259d0a7f7643d5d4606b7a0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7e29414a0bc0ba815f646b32c52fbbf11ff7d9a6fef88064e5a2bbafd13c012 0.600000000000 1522023 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": 1051718, "vin": [ { "gen": { "height": 1051708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7e29414a0bc0ba815f646b32c52fbbf11ff7d9a6fef88064e5a2bbafd13c012" } } ], "extra": [ 1, 170, 57, 122, 96, 176, 46, 50, 246, 67, 41, 95, 198, 94, 68, 204, 234, 129, 121, 209, 72, 120, 37, 157, 10, 127, 118, 67, 213, 212, 96, 107, 122, 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