Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5947b726742c9b8b87331a821339318386324f13d111f93ae1c50d7100ff60c0

Tx prefix hash: 23407d345bb387917901f3b308356a55b0b4151320cdda391f91e81fa1a53017
Tx public key: 86a2aab46201b16a1d8e2d23f26c2d01d32a1ba9e53b54673d4c09b400c24628
Timestamp: 1719855253 Timestamp [UCT]: 2024-07-01 17:34:13 Age [y:d:h:m:s]: 01:130:22:00:31
Block: 1056348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352102 RingCT/type: yes/0
Extra: 0186a2aab46201b16a1d8e2d23f26c2d01d32a1ba9e53b54673d4c09b400c246280211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f58242723ef4a554aa99bc5f5032dc9f0a928dbe7f7c994b2b0ddb150483ade0 0.600000000000 1526761 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": 1056358, "vin": [ { "gen": { "height": 1056348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f58242723ef4a554aa99bc5f5032dc9f0a928dbe7f7c994b2b0ddb150483ade0" } } ], "extra": [ 1, 134, 162, 170, 180, 98, 1, 177, 106, 29, 142, 45, 35, 242, 108, 45, 1, 211, 42, 27, 169, 229, 59, 84, 103, 61, 76, 9, 180, 0, 194, 70, 40, 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