Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c38938c41591ad2b8b72998e39d6840a964a5be369b5b501bfb0dc1848853d73

Tx prefix hash: a4dd1f39df4f4161117d3a53412e12cbe6331d8896a32dbc2ac426c31a6603d5
Tx public key: 0c09a92f9e8a3f79cd19c2ecf140209cbe32ac5d5b28e879a3f388aab24606b3
Timestamp: 1698407592 Timestamp [UCT]: 2023-10-27 11:53:12 Age [y:d:h:m:s]: 01:223:20:02:09
Block: 878764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421013 RingCT/type: yes/0
Extra: 010c09a92f9e8a3f79cd19c2ecf140209cbe32ac5d5b28e879a3f388aab24606b30211000000024b8f5122000000000000000000

1 output(s) for total of 0.752145114000 dcy

stealth address amount amount idx
00: f784cb7fe3557eb920d22f58e8d83d4eb2fb793a37b953df193ba3f90d548e73 0.752145114000 1334238 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": 878774, "vin": [ { "gen": { "height": 878764 } } ], "vout": [ { "amount": 752145114, "target": { "key": "f784cb7fe3557eb920d22f58e8d83d4eb2fb793a37b953df193ba3f90d548e73" } } ], "extra": [ 1, 12, 9, 169, 47, 158, 138, 63, 121, 205, 25, 194, 236, 241, 64, 32, 156, 190, 50, 172, 93, 91, 40, 232, 121, 163, 243, 136, 170, 178, 70, 6, 179, 2, 17, 0, 0, 0, 2, 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