Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fad71981eff29cb444e1e39510b0c071f45215c95ef233b3cb6b3184815f5f4

Tx prefix hash: d292d2aa11d71de9d40ba364a10b44185fd0742e6a8077c2cf8b6091aa58cb82
Tx public key: 48bf562f3068e3d4a21ea6892588951f4ec99384e69f7b3e7281644878853b55
Timestamp: 1737805100 Timestamp [UCT]: 2025-01-25 11:38:20 Age [y:d:h:m:s]: 00:143:06:38:04
Block: 1204976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102137 RingCT/type: yes/0
Extra: 0148bf562f3068e3d4a21ea6892588951f4ec99384e69f7b3e7281644878853b550211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3a84e6fac69316ca49d0d97bf146329b3099d1f9d91b738c912f12decf4a3f0 0.600000000000 1691671 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": 1204986, "vin": [ { "gen": { "height": 1204976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3a84e6fac69316ca49d0d97bf146329b3099d1f9d91b738c912f12decf4a3f0" } } ], "extra": [ 1, 72, 191, 86, 47, 48, 104, 227, 212, 162, 30, 166, 137, 37, 136, 149, 31, 78, 201, 147, 132, 230, 159, 123, 62, 114, 129, 100, 72, 120, 133, 59, 85, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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