Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83e9046f895c87d6eaac9285401f64eb43d164db3edba291590a9f26c4f563e6

Tx prefix hash: a9a369df66f34cab55c2f31d2737c482d58cf02096fd15155180614a96e221ee
Tx public key: 640ec0302c5225c94ab8b944abbc5a68786f87b91fba3a1f732d2956269f5ecf
Timestamp: 1715641250 Timestamp [UCT]: 2024-05-13 23:00:50 Age [y:d:h:m:s]: 00:226:01:44:31
Block: 1021414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161819 RingCT/type: yes/0
Extra: 01640ec0302c5225c94ab8b944abbc5a68786f87b91fba3a1f732d2956269f5ecf0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c309602521751c9dc958f3f671174a36f8f9d819074f8bdbfd1e6bf1ccaf42e 0.600000000000 1485727 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": 1021424, "vin": [ { "gen": { "height": 1021414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c309602521751c9dc958f3f671174a36f8f9d819074f8bdbfd1e6bf1ccaf42e" } } ], "extra": [ 1, 100, 14, 192, 48, 44, 82, 37, 201, 74, 184, 185, 68, 171, 188, 90, 104, 120, 111, 135, 185, 31, 186, 58, 31, 115, 45, 41, 86, 38, 159, 94, 207, 2, 17, 0, 0, 0, 2, 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