Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 022e6b267133c51718c306ea44a8e4f3765d09e7b612dcd52f3fc65898954637

Tx prefix hash: 747587a72b0c78f880a97788d0d6c7d81109c2b81033d874985ec7c936910075
Tx public key: c16764b09c68eb4012b9d64cc79f16d8e1a61340b487f88093c4ab3ccb982e9b
Timestamp: 1706297628 Timestamp [UCT]: 2024-01-26 19:33:48 Age [y:d:h:m:s]: 01:053:01:03:16
Block: 943928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299020 RingCT/type: yes/0
Extra: 01c16764b09c68eb4012b9d64cc79f16d8e1a61340b487f88093c4ab3ccb982e9b0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b31fd9e1b7351e42fed58de81e59710e563a8143b1841a553b05e3ab29f5db96 0.600000000000 1402154 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": 943938, "vin": [ { "gen": { "height": 943928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b31fd9e1b7351e42fed58de81e59710e563a8143b1841a553b05e3ab29f5db96" } } ], "extra": [ 1, 193, 103, 100, 176, 156, 104, 235, 64, 18, 185, 214, 76, 199, 159, 22, 216, 225, 166, 19, 64, 180, 135, 248, 128, 147, 196, 171, 60, 203, 152, 46, 155, 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