Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0313e3a353e6e1d656dfa0ab627e699663260841aa0a0533f78bfbe2067e0a7a

Tx prefix hash: 5a4e6013ea915905f7f8312f34073a83f5503826acf9773241276579ff52e62e
Tx public key: 93a55a5da6633afa3c89a923459877b0c9e29278e88c8d20c7d24f21d7d214b4
Timestamp: 1709530067 Timestamp [UCT]: 2024-03-04 05:27:47 Age [y:d:h:m:s]: 01:017:12:21:53
Block: 970763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273511 RingCT/type: yes/0
Extra: 0193a55a5da6633afa3c89a923459877b0c9e29278e88c8d20c7d24f21d7d214b40211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54da0411341c44ac4b81b734538ce1ab0568d8796fa215e89adae56e3e2108a6 0.600000000000 1430624 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": 970773, "vin": [ { "gen": { "height": 970763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54da0411341c44ac4b81b734538ce1ab0568d8796fa215e89adae56e3e2108a6" } } ], "extra": [ 1, 147, 165, 90, 93, 166, 99, 58, 250, 60, 137, 169, 35, 69, 152, 119, 176, 201, 226, 146, 120, 232, 140, 141, 32, 199, 210, 79, 33, 215, 210, 20, 180, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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