Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ff6b6ba69edbd9e7f0ecdcace451c583c189bdd37fe076246048dc0d0953162

Tx prefix hash: f29a7807a534785610221bfd24caf7b73540886a47be83bd6ce784177841e2e0
Tx public key: f3dd0b1116b2152b9a99b2a1274d0e4505d87fa97fe503d8d2892a80ec488d8b
Timestamp: 1694809804 Timestamp [UCT]: 2023-09-15 20:30:04 Age [y:d:h:m:s]: 01:195:12:00:33
Block: 848901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400812 RingCT/type: yes/0
Extra: 01f3dd0b1116b2152b9a99b2a1274d0e4505d87fa97fe503d8d2892a80ec488d8b02110000000e4b8f5122000000000000000000

1 output(s) for total of 0.944579791000 dcy

stealth address amount amount idx
00: 03b5225b2f31c41bd5a0aece80598fa05550f8527f62c4b4186f1bacbe74437e 0.944579791000 1302535 of 0

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": 848911, "vin": [ { "gen": { "height": 848901 } } ], "vout": [ { "amount": 944579791, "target": { "key": "03b5225b2f31c41bd5a0aece80598fa05550f8527f62c4b4186f1bacbe74437e" } } ], "extra": [ 1, 243, 221, 11, 17, 22, 178, 21, 43, 154, 153, 178, 161, 39, 77, 14, 69, 5, 216, 127, 169, 127, 229, 3, 216, 210, 137, 42, 128, 236, 72, 141, 139, 2, 17, 0, 0, 0, 14, 75, 143, 81, 34, 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