Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f97cb3843958c0ef0a23646589868f472f24fb1b25bdd3e668c4c23c8d83795d

Tx prefix hash: 4d4b08367046b1b0777e240aa70936e37a22dada671a9d0f1e9c3cfcecb3a68f
Tx public key: c85991fbeaa6ccd3f73b5781f9d9d9bc120df8b707458b435ca9267c95940b36
Timestamp: 1700954883 Timestamp [UCT]: 2023-11-25 23:28:03 Age [y:d:h:m:s]: 01:201:11:23:42
Block: 899657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405134 RingCT/type: yes/0
Extra: 01c85991fbeaa6ccd3f73b5781f9d9d9bc120df8b707458b435ca9267c95940b36021100000003e08532b6000000000000000000

1 output(s) for total of 0.641302418000 dcy

stealth address amount amount idx
00: 37158445d8bfc8f32d17e1560746aaec9beb96c7e394a2d1499f41d8bfb8fc1f 0.641302418000 1356118 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": 899667, "vin": [ { "gen": { "height": 899657 } } ], "vout": [ { "amount": 641302418, "target": { "key": "37158445d8bfc8f32d17e1560746aaec9beb96c7e394a2d1499f41d8bfb8fc1f" } } ], "extra": [ 1, 200, 89, 145, 251, 234, 166, 204, 211, 247, 59, 87, 129, 249, 217, 217, 188, 18, 13, 248, 183, 7, 69, 139, 67, 92, 169, 38, 124, 149, 148, 11, 54, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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