Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68df418128749dca2676167d75f346f606c067f09e009493b4903cb908ef9628

Tx prefix hash: 044c9735a0a246abe7ab49be6668ca7b4e2846007c61180e6811bfa1d0eb351f
Tx public key: f34345522d67dff2dac2aa022b2aa6dd0043a38ae8101a9fd5885b5281c27561
Timestamp: 1707956249 Timestamp [UCT]: 2024-02-15 00:17:29 Age [y:d:h:m:s]: 01:283:03:23:28
Block: 957700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 461139 RingCT/type: yes/0
Extra: 01f34345522d67dff2dac2aa022b2aa6dd0043a38ae8101a9fd5885b5281c275610211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36918b742cee2f63c9f88a8ebbf5270003b7514453590564519fd8b7b34635b4 0.600000000000 1417047 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": 957710, "vin": [ { "gen": { "height": 957700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36918b742cee2f63c9f88a8ebbf5270003b7514453590564519fd8b7b34635b4" } } ], "extra": [ 1, 243, 67, 69, 82, 45, 103, 223, 242, 218, 194, 170, 2, 43, 42, 166, 221, 0, 67, 163, 138, 232, 16, 26, 159, 213, 136, 91, 82, 129, 194, 117, 97, 2, 17, 0, 0, 0, 4, 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